Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@services/platform/app/components/ui/data-display/copyable-timestamp.tsx`:
- Around line 69-74: The current logic appends timezoneShort to baseFormatted
regardless of customFormat, causing customFormat to be improperly altered;
update the construction of formatted (and its use of baseFormatted/formatDate)
so that timezoneShort is only appended when showTimezone is true AND no
customFormat is provided (i.e., respect customFormat as a full override). Locate
the variables baseFormatted, formatted, formatDate, customFormat, showTimezone,
timezoneShort and dateObj in copyable-timestamp.tsx and change the conditional
that builds formatted to skip post-processing of baseFormatted when customFormat
is present.

In
`@services/platform/app/features/documents/components/__tests__/document-preview-routing.test.tsx`:
- Around line 58-74: The mock implementation of lazyComponent has a race where
the closure variable Component is set asynchronously but the returned component
reads it synchronously, so tests never re-render; update the mock
(lazyComponent) to use React state/effect inside the returned function component
so that when the factory promise resolves it calls setState and triggers a
re-render (i.e., use React.useState/React.useEffect to hold the resolved
component and update it on factory().then(...)), ensure you import React (import
* as React from 'react') in the mocks file, and remove/replace relying on
flushMicrotasks by using Testing Library's waitFor in tests if needed.

In
`@services/platform/app/features/documents/components/document-preview-dialog.tsx`:
- Around line 59-65: The preview currently resolves a single team via the
teamName useMemo (checking doc.teamId) which drops multi-team assignments;
change this to map the document's team array (e.g., doc.teams or doc.teamIds—use
the actual property on the document) to find all matching entries in the teams
list and return a joined label (e.g., comma-separated names), and if that
resulting array is empty fall back to the organization-wide label; update the
same logic where a similar single-team resolution appears (the other occurrence
referenced around lines 114-116) to use the document's team array and the same
fallback behavior.

In
`@services/platform/app/features/documents/components/document-preview-image.tsx`:
- Around line 23-33: The component's isLoading/hasError state is not reset when
the incoming url prop changes, so reuse of the component keeps previous
load/error state; add a useEffect that watches the url variable and resets
setIsLoading(true) and setHasError(false) whenever url changes so each new image
starts in the loading state; keep the existing handleLoad and handleError
callbacks but ensure the effect runs before a new load begins to avoid showing
stale error/success UI.
- Line 5: The import for ZoomPanViewer in document-preview-image.tsx is
incorrect; update the import to match the actual export and file location (use
the correct relative path or named/default export) so knip can resolve it—locate
where ZoomPanViewer is defined/exported, replace the current import line with
the exact module path and export form that matches that definition, and verify
the component builds.

In `@services/platform/app/features/documents/components/document-preview.tsx`:
- Around line 148-150: The IMAGE_EXTENSIONS set currently excludes TIFF/TIF so
files with extension 'tiff' or 'tif' fall through to download-only; update the
IMAGE_EXTENSIONS constant to include 'tiff' and 'tif' (or add a normalized check
for these extensions where extension is derived) so DocumentPreviewImage is
returned for TIFFs, and optionally add a comment or a feature flag to handle
browsers that don't render TIFF by falling back to conversion/preview generation
in the preview pipeline.

In
`@services/platform/app/features/documents/components/document-team-tags-dialog.tsx`:
- Around line 190-239: The group of checkboxes currently rendered with <div
role="group"> should be a native fieldset with a visually hidden legend to
satisfy accessibility linting; replace the outer <div role="group"
aria-label={tDocuments('teamTags.title')}> with a <fieldset> keeping the same
classNames and inner structure, add a visually hidden <legend> containing
tDocuments('teamTags.title'), and remove the role/aria-label from the wrapper;
ensure existing handlers and props (handleSelectOrgWide, handleToggleTeam,
teams, selectedTeamIds, Checkbox, Text) and the button classes/disabled logic
remain unchanged so behavior and styling are preserved.
- Around line 141-161: The footer and the org-wide control are currently
conditionally hidden by hasTeams, preventing submitting teamIds: [] when there
are no teams; update the JSX in document-team-tags-dialog.tsx so the Save/Cancel
footer (the Button group using handleSubmit and handleClose with
isSubmitting/hasChanges) always renders regardless of hasTeams, and ensure the
org-wide control (the control rendered around lines 164-188) is rendered even
when hasTeams is false; keep the team-selection UI conditional on hasTeams but
allow handleSubmit to accept and submit an empty teamIds array when no teams are
present.

In `@services/platform/app/features/documents/components/documents-table.tsx`:
- Around line 192-197: The team filter uses doc.teamId (single value) instead of
checking all assigned teams, so documents with multiple team assignments are
missed; update the filter in the documents-table component to check doc.teamIds
(array) against selectedTeamIds by creating a Set from selectedTeamIds and using
Array.prototype.some (or Array.prototype.every depending on desired semantics)
to test if any of doc.teamIds exist in the set (e.g., teamIdSet.has(id) inside
doc.teamIds.some). Ensure you keep the same filtered variable and only apply
this change inside the existing selectedTeamIds.length > 0 block where
doc.teamId is currently referenced.

In
`@services/platform/app/features/documents/components/onedrive-import/onedrive-file-table.tsx`:
- Around line 47-48: The code is using timezoneShort from useFormatDate() (which
uses new Date()) so the suffix reflects "now" rather than the file's timestamp;
instead compute the timezone suffix from the row's timestamp and use formatDate
with the row's lastModified value so both the human date string and the suffix
are normalized to that specific time. Concretely, replace uses of timezoneShort
and Date(row.lastModified) in the OneDrive file table rendering (references:
useFormatDate(), timezoneShort, formatDate(), lastModified) with a timezone
derived from new Date(row.lastModified) (or call a date-aware helper on that
timestamp) and call formatDate(row.lastModified) everywhere (including the other
occurrences around the same component at the noted locations).

In
`@services/platform/app/features/documents/hooks/use-documents-table-config.tsx`:
- Around line 199-211: The runtime filter(Boolean) on names (computed from
teamIds.map(id => teamMap.get(id))) doesn't narrow (string | undefined)[] to
string[]; update the filter to use a type predicate such as filter((n): n is
string => n !== undefined) so that names becomes string[] for subsequent
slice/join operations and functions/constants like MAX_VISIBLE, names, teamIds,
and teamMap are handled with correct TypeScript typing.

In `@services/platform/convex/documents/validators.ts`:
- Around line 68-69: Change the validator and data flow so teamIds is the
canonical always-present array: replace the optional schema
v.optional(v.array(v.string())) for the teamIds field in validators.ts with a
required v.array(v.string()), update any corresponding validators that reference
teamId/teamIds, and in the document transform function (the place that
normalizes legacy documents) coerce missing/undefined teamIds to an empty array
([]). Also update the TypeScript shape in services/platform/types/documents.ts
to declare teamIds: string[] so the runtime validator, transform, and type
definitions are consistent.

---

Outside diff comments:
In `@services/platform/convex/documents/mutations.ts`:
- Line 97: The comment points out that createDocumentFromUpload still accepts a
single teamId while updateDocument accepts teamIds[], causing asymmetry; decide
whether uploads should support multiple teams and, if so, change the schema for
createDocumentFromUpload (and the other occurrence around the second spot) from
teamId: v.optional(v.string()) to teamIds: v.optional(v.array(v.string())) and
update any code paths that construct or persist the document (e.g., the
createDocumentFromUpload handler and related helpers) to accept and iterate the
array; if multi-team on upload is intentionally unsupported, instead add a short
inline comment near createDocumentFromUpload explaining that single-team uploads
are deliberate to avoid confusion.

In `@services/platform/convex/documents/update_document.ts`:
- Around line 36-48: The current team validation in update_document.ts only
checks membership via getUserTeamIds and can allow attaching to teams from other
organizations; update the logic to, for each id in args.teamIds, load the team
record (e.g., via the existing team loader function such as getTeamById or
equivalent) and verify the team exists and that team.organizationId ===
document.organizationId before accepting it; if any team is missing or has a
different organizationId, throw a descriptive error like "Cannot assign document
to a team in a different organization"; retain the existing user membership
check (getUserTeamIds and userTeamSet) so you enforce both existence/ownership
and that the user belongs to the target teams.